Add the document to backfill using tx_meta #273
Conversation
|
Steps outlined in the document added in this PR. I will add screenshots and links for confirming test results Library in GCS bucket
JS UDFResults confirmations:
Sample check against horizon (testnet) ✅
Next steps:
|
backfill.md
Outdated
| ) | ||
| AS r""" | ||
| let txe = StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, 'base64'); | ||
| let tx = txe.feeBump(); | ||
| let sourceAccount = StellarBase.encodeMuxedAccountToAddress(tx.tx().feeSource()); | ||
| return sourceAccount | ||
|
|
There was a problem hiding this comment.
Thanks @Shaptic for the helps here 🙌
lint pass?
amishas157
force-pushed
the
feature/hubble-499/support-backfills-using-txmeta
branch
from
19d575e to
ea28305
Compare
backfill.md
Outdated
There was a problem hiding this comment.
Very nice!
Do you think we should make a new directory for this .md? It seems misplaced in the base directory. Maybe like a notes or scripts directory? Open to naming ideas
There was a problem hiding this comment.
docs/? I am also thinking to include migrations directory, where we manually track any udfs run we apply
backfill.md
Outdated
|
|
||
| Following is example to extract FeeAccountMuxed: | ||
|
|
||
| ``` |
There was a problem hiding this comment.
suggestion: add javascript tag here for syntax highlighting
There was a problem hiding this comment.
Addressed in d5884a2
backfill.md
Outdated
| let txe = StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, 'base64'); | ||
| let tx = txe.feeBump(); | ||
| let sourceAccount = StellarBase.encodeMuxedAccountToAddress(tx.tx().feeSource()); | ||
| return sourceAccount |
There was a problem hiding this comment.
| let txe = StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, 'base64'); | |
| let tx = txe.feeBump(); | |
| let sourceAccount = StellarBase.encodeMuxedAccountToAddress(tx.tx().feeSource()); | |
| return sourceAccount | |
| return StellarBase.encodeMuxedAccountToAddress( | |
| StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, 'base64') | |
| .feeBump() | |
| .tx() | |
| .feeSource() | |
| ); |
😉
PR Checklist
PR Structure
otherwise).
Thoroughness
Release planning
semver, and I've changed the name of the BRANCH to release/_ , feature/_ or patch/* .
What
This PR add instructions on backfill historical data using tx_meta
Why
Airflow runs can be time and money consuming. To ease up the migrations, JS UDF can be convenient.
Known limitations
To be figures: Cost of UDF (they should be cheap most likely)